docs: clarify new-service CPU/RAM defaults#269
Open
mintlify[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Update the resource allocation section of the application services guide to reflect the new default request values for newly added services (0.5 CPU / 512 MB), and note that sandbox projects use smaller defaults.
Changes
Context
The dashboard now caps the auto-filled CPU/RAM defaults for newly added services at 0.5 CPU and 512 MB, regardless of cluster node size. Previously, on clusters with large application nodes, defaults were sized as a fraction of node capacity and could land much higher than most first services need, forcing users to scale the sliders down before deploying. Slider maximums are unchanged.